Process-level metadata inference and mapping from document annotations

ABSTRACT

A user annotation entered in association with a content document of a workflow process executed in association with a metadata context-driven processing system is detected. The user annotation entered in association with the content document is analyzed according to a process-level context associated with the content document within the workflow process. Process-level metadata of the workflow process is inferred based upon the analysis of the user annotation according to the process-level context. The inferred process-level metadata is stored as part of the process-level context of the workflow process.

BACKGROUND

The present invention relates to document annotation processing. Moreparticularly, the present invention relates to process-level metadatainference and mapping from document annotations.

Documents may be used to compartmentalize content in association withworkflow and other processes. Documents may be modified during a givenphase of a workflow process by a person designated to evaluate andupdate the content in association with duties related to that phase ofthe workflow process. The updated content may be stored for use insubsequent phases of a workflow process, and the content may be furthermodified during one or more subsequent phases of the workflow process.As such, the documents capture and represent the resulting work productof the workflow process.

BRIEF SUMMARY

A method includes detecting, by a processor, a user annotation enteredin association with a content document of a workflow process executed inassociation with a metadata context-driven processing system; analyzingthe user annotation entered in association with the content documentaccording to a process-level context associated with the contentdocument within the workflow process; inferring process-level metadataof the workflow process based upon the analysis of the user annotationaccording to the process-level context; and storing the inferredprocess-level metadata as part of the process-level context of theworkflow process.

A system includes a memory; and a processor programmed to: detect a userannotation entered in association with a content document of a workflowprocess executed in association with a metadata context-drivenprocessing system; analyze the user annotation entered in associationwith the content document according to a process-level contextassociated with the content document within the workflow process; inferprocess-level metadata of the workflow process based upon the analysisof the user annotation according to the process-level context; and storethe inferred process-level metadata within the memory as part of theprocess-level context of the workflow process.

A computer program product includes a computer readable storage mediumhaving computer readable program code embodied therewith, where thecomputer readable program code when executed on a computer causes thecomputer to: detect a user annotation entered in association with acontent document of a workflow process executed in association with ametadata context-driven processing system; analyze the user annotationentered in association with the content document according to aprocess-level context associated with the content document within theworkflow process; infer process-level metadata of the workflow processbased upon the analysis of the user annotation according to theprocess-level context; and store the inferred process-level metadata aspart of the process-level context of the workflow process.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Figure (FIG.) 1 is a block diagram of an example of an implementation ofa system for process-level metadata inference and mapping from documentannotations according to an embodiment of the present subject matter;

Figure (FIG.) 2 is a block diagram of an example of an implementation ofa core processing module capable of performing process-level metadatainference and mapping from document annotations according to anembodiment of the present subject matter;

Figure (FIG.) 3 is a flow chart of an example of an implementation of aprocess for process-level metadata inference and mapping from documentannotations according to an embodiment of the present subject matter;

Figure (FIG.) 4A is a flow chart of an example of an implementation ofinitial processing within a process for process-level metadata inferenceand mapping from document annotations by correlation of categorizedannotation content and available process-level metadata values ofrelated process-level metadata types, and mapping from inferredprocess-level metadata to content-level metadata of other content itemsaccording to an embodiment of the present subject matter; and

Figure (FIG.) 4B is a flow chart of an example of an implementation ofadditional processing within a process for process-level metadatainference and mapping from document annotations by correlation ofcategorized annotation content and available process-level metadatavalues of related process-level metadata types, and mapping frominferred process-level metadata to content-level metadata of othercontent items according to an embodiment of the present subject matter

DETAILED DESCRIPTION

The examples set forth below represent the necessary information toenable those skilled in the art to practice the invention and illustratethe best mode of practicing the invention. Upon reading the followingdescription in light of the accompanying drawing figures, those skilledin the art will understand the concepts of the invention and willrecognize applications of these concepts not particularly addressedherein. It should be understood that these concepts and applicationsfall within the scope of the disclosure and the accompanying claims.

The subject matter described herein provides process-level metadatainference and mapping from document annotations. The present technologyintroduces a process-level metadata inference component that operates todetect an act of a user annotating a document (e.g., content associatedwith a workflow process). The process-level metadata inference componentinfers process-level metadata from the detected annotations, maps theinferred process-level metadata to process-level objects, and initiatesprocess-level operations in response to the changes in process-levelmetadata. As such, the present subject matter provides an autonomoustechnological bridge between user annotations entered in associationwith documents and process-level metadata that is programmaticallyinferred from the user annotations.

The programmatically-inferred process-level metadata may be associatedwith process-level objects that are distinct from the documents/contentwith which the user annotations are originally entered and associated.The user annotations on the documents remain intact, and process-levelfunctionality may autonomously proceed to or invoke one or moresubsequent phases of workflow processing. The subsequent phase(s) of theprocess-level functionality may utilize the original unaltered userdocument annotations to further facilitate and guide the processing ofthe respective subsequent phase(s) of the process-level functionalityand to allow users involved in the subsequent phase(s) of the workflowprocess to view the original annotations. By providing integratedprocess-level inference technology in combination with usability oforiginal document/content annotations, the inferred process-levelmetadata enhances process-level context and programmatic decision makingrelated to process-level functionality, while maintaining experientialhuman factor aspects related to workflow process interaction by workflowparticipants.

The present technology provides inference and mapping of a wide varietyof document annotations to process-level metadata properties for one ormore process-level objects. Annotations entered in association with anindividual document may be individually analyzed or analyzed as a set,and process-level metadata properties associated with the document'scontainer object may be inferred from the document annotations. Forexample, metadata for a case or case folder that contains a documentimage (e.g., an x-ray, insurance application, etc.) may be inferred fromannotations entered on an image of the document.

By leveraging programmatic inference of process-level metadata fromdocument annotations, process-level metadata entry may be madeconsistent across multiple process-level entities (e.g., across multiplecases, multiple claims, etc.). Further, process-level metadata entryerrors may be reduced, efficiency of process-level activities may beimproved, and duplication of information may be reduced. As such, thepresent technology may be leveraged to increase productivity of workflowparticipants and to replicate quality/consistency of process-leveloutcomes, and as a result may also reduce time requirements and costsassociated with workflow process-level activities.

Document and image-based annotations may be processed and analyzed usingimage recognition technologies, such as optical character recognition(OCR), and handwriting recognition technology to capture the content ofthe respective annotations. The captured annotation content may then beanalyzed to determine how the captured annotation content relates toprocess-level activities. The relationship between the capturedannotation content as it relates to process-level activities may bedocumented in the form of a change to process-level metadata of aprocess-level object associated with the annotated document. Workflowprocess-level activity may be invoked to further process the changedprocess-level metadata, such as performing an additional action relatedto processing within the respective workflow/process, including furtherprocessing of the annotated document/image itself as appropriate for thegiven implementation.

For example, where a case management system is used to process loanapplications, a scanned loan application document attached to a loanrequest case/folder may have programmatically-captured hand-written orotherwise notated annotations on or associated with the document. Theannotations may include requests for additional employment history,income verification, an approved loan amount, or other annotations asappropriate for the given implementation. The case or case folder as aprocess-level object may have process-level metadata properties thattrack these types of requests, as well as other pertinent informationrelating to the case (e.g., the particular loan application). The sameprocess-level metadata properties may also be used to automaticallyinitiate other process-level processing of the loan applicant's case. Tofurther the present example, analysis of the annotations may be utilizedto update process-level metadata properties to request the additionalinformation and/or to automatically launch a process to obtain theadditional employment history or income verification. Additionally, theupdated process-level metadata may initiate a next step in theassociated workflow of the loan process, such as where an approved loanamount is specified and processing to prepare closing documents for theloan may be initiated.

As another example, where a medical client information processing systemthat processes medical cases is utilized, an x-ray may includeannotations entered by a radiologist onto an electronic or physical copyof the image, such as an arrow identifying a bone fracture, and acomment related to a severity of the bone fracture. The case or casefolder as a process-level object may have process-level metadataproperties that track radiological and other types of images, as well asother pertinent information relating to the case (e.g., the particularpatient). The same process-level metadata properties may also be used toautomatically initiate other process-level processing of the patient'scase. To further the present example, analysis of the annotations may beutilized to update process-level metadata properties to indicate thatthe patient is to have a cast applied to immobilize the patient'sfracture, and an automated notification may be generated to indicatethat the patient is to be moved to an available room to have the castapplied.

Many other possible implementations of the present technology arepossible. All such possible implementations are considered to be withinthe scope of the present technology.

It should be noted that several terms are utilized to refer tocategories of elements or may be used interchangeably to assist withdescription of the present technology. For example, the term“annotation” refers to a hand-written or electronic notation associatedwith a document that represents/captures a user's inspection of andanalysis of the document (e.g., factual findings or a decision). Assuch, the term annotation is distinct from the term process-levelmetadata as used herein and defined further below. It is furtherunderstood that a document annotation as described herein is analyzed toinfer separate and distinct process-level metadata.

The terms “document,” “process content,” and similar terms as usedherein may include data upon which a process operates, such as a form(e.g., web-fillable form), an image (e.g., a photographic image, x-ray,etc.), a user request object, an application object (e.g., a loanapplication, etc.), a portable document format (PDF) file, or other formof data or content object. As such, these terms refer to anydata/content that may be associated with and operated upon as part of aprocess or workflow context.

The term “process-level metadata” and similar terms as utilized hereinrefer to formalized process-level entries that guide and informprocess-level actions associated with a workflow. As such, theprocess-level metadata inference and mapping from document annotations,as described herein, forms a mapping of unstructured user notationsentered in association with documents into formalized process-level dataentries that may be used to invoke and guide process-level activities.

The terms “process-level context,” “workflow context” and similar termsas used herein refer to a formalized process-level association ofprocess content. As such, collections of documents and/or processcontent associated with a particular project or series of activities maybe considered to share the same “context” for process-level operations.A “workflow relationship object” represents process-level context for aworkflow. Examples of a process-level or workflow context, and thereby aworkflow relationship object, may include a container object, such as afolder, a case, a request, client/customer information, or other form ofrelationship or association with which documents may be formallycompartmentalized and related. A “client” or a “case” associated with aclient may be considered to form a process-level context for purposes ofthe present description. Collections of process-level metadata may formcontext associated with a workflow process that identify particularprocess-level attributes associated with the particular process-levelcontext (e.g., the client, case, etc.). The terms process-level contextand workflow context are used interchangeably herein to refer to anysuch association of content objects, and may be referred to hereingenerally as “context” for ease of description as defined above with theunderstanding that any reference to one of the respective terms may beapplied to any of the other respective terms as defined above and asappropriate for a given implementation.

Additionally, the terms “process-level structure,” “process-levelobject,” “workflow-processing object,” are used interchangeably hereinand represent a structured association or collection of process-levelmetadata (process-level context) about a particular categorizedprocess/workflow activity. A “container object” may be considered aprocess-level folder/structure that compartmentalizes the process-levelcontext/metadata and associates that process-level context with processcontent/documents. For example, a case folder in a case managementsystem is an example of a process-level structure or container objectthat associates case metadata (e.g., patient name, etc.) with casedocuments (e.g., x-ray images, etc.) for a particular case/client. Aclaim folder in an insurance claims management system is another exampleof a process-level structure or container object that associates claimmetadata (e.g., insured name, insurance limits, etc.) with claimdocuments (e.g., insurance claim forms, etc.) for a particular insuredindividual. As such, a container object is considered a structuredprocess-level object that is instantiated and/or stored within a memorydevice for purposes of the present description. The terms “process-levelobject,” “container,” and “container object” may be used interchangeablyherein as appropriate for a given example with the understanding thatany such reference to one of the respective terms may be applied to anyof the other respective terms as defined above and as appropriate for agiven implementation.

Additionally, a “workflow processing system,” “case processing system,”“metadata context-driven processing system,” and similar terms as usedherein may be considered to refer systems that utilize process-levelmetadata/context to guide and control workflow processing. Examples of ametadata context-driven processing system include a business processingmanagement (BPM) system, an enterprise content management (ECM) system,a work flow management system, a case management system, or any otherform of system that facilitates and provides technology for processingof workflow-related activities. As such, the term metadatacontext-driven processing system is used herein to refer to any suchtechnological system.

Further, as used herein, the terms “invoke” and “initiate” as usedwithin the context of a process-level “action” and similar terms referto initiation/launching of processing based upon an inference of and/ora change to process-level metadata from annotations. For example,invocation of a workflow action may include starting a process-levelactivity or step (e.g., progressing a case to the next stage ofprocessing), initiation/launching of a work flow or portion of aworkflow, and initiation/launching of a service (e.g., a call to aweb-service operation with parameters based upon inferred metadata).

An example of metadata inference and invocation of web-serviceoperations from annotations includes inferring parameters that specifythe designated start time for a particular task from annotations. Anexample process-level initiation of web-service operations includesstarting a web-based task manager service with the inferred parametersto schedule a launch and run a particular task. Another example ofmetadata inference and invocation of web-service operations fromannotations includes inferring parameters that specify adifference/change in billing for a client (e.g., a patient of a doctor)and starting a billing web service with the inferred parameters toadjust the client billing (e.g., to create an invoice, etc.).

Invocation of a process-level action may also include operations, suchas, initiation/launching of an operation (e.g., a case operation such assplitting a case, marking a case as completed, etc.), initiating updatesto a search engine to recognize inferred process-level metadata toexpose the inferred process-level metadata to the search facilities(e.g., expose a newly opened or closed case as a potential search resultfor “open cases” or “closed cases,” respectively), creation of a recordof a change to process-level metadata resulting from inference of themetadata from the annotation to declare the annotations or set ofannotations and the inferred metadata as records, or other forms ofinitiation of processing within a workflow processing system.

As such, the process-level metadata inference and mapping from documentannotations, as described herein, operates as a new event trigger formultiple forms of processing in association with process-level andworkflow management systems. Accordingly, invocation of a process-levelaction is used herein to refer to initiation of any suchannotation-originated inferred-metadata-based processing event.

Additionally, the inferred and updated process-level metadata may beevaluated to determine whether any other related content items (e.g.,documents) in the process-level container (e.g., case, folder, etc.)have a relationship to the inferred process-level metadata. Where such arelationship is determined, the related content-level metadata values ofthe other related content items may be updated. As such, the presenttechnology provides mapping from annotations on documents at thecontent-level up to metadata at the process-level, and the updatedinferred metadata at the process-level may further be utilized to updatemetadata back down at the content-level in association with othercontent items/documents in the respective container object. Accordingly,the present technology provides a sophisticated cross-hierarchicalpropagation of metadata from inferred annotations on documents up to theprocess-level and back down to the content-level and other contentitems.

It should be noted that conception of the present subject matterresulted from recognition of certain limitations associated withdocument processing within the context of workflow processes. It wasobserved with respect to previous workflow processing systems that auser may annotate a document, such as an image document, withannotations that may include identifiers of portions of the documentand/or written notations. For example, it was observed that aradiologist may annotate a patient x-ray document with an arrow thatidentifies an area of the image associated with written details thatspecify analysis of the x-ray, or that an insurance adjuster mayannotate a vehicle photographic image with a circle that identifies anarea of damage associated with written details of the vehicleinspection, or that a loan processing officer may place an asterisk on ascanned image of a loan application that identifies an area of the loanapplication for which written details specify additional informationthat is needed to complete the loan application. It was further observedthat each user may enter such annotations differently from other usersand that additional business-level processing may be appropriate in eachsituation after the user annotates the image. However, it was furtherobserved that there is no prior technology by which to autonomouslyevaluate different forms of annotations of different users or by whichto infer workflow process-level metadata from such an evaluation ofdifferent types of annotations. It was further observed that there wasno prior technology by which to autonomously associate any such inferredworkflow process-level metadata with a container or business objectwithin a workflow process (e.g., with a case folder of the patient, orwith an insurance claim of an insured motorist, or with the loanapplicant case folder). It was additionally observed that there was noprior technology by which to invoke appropriate business-levelprocessing from inferred workflow process-level metadata. From theseobservations, it was determined that it was desirable to providetechnology by which workflow process-level metadata may be autonomouslyinferred from evaluation of image annotations and autonomously mapped to(associated with) containers or business objects with which the imagesor documents are associated. It was further determined that it wasdesirable to provide technology to invoke appropriate workflow processactivities based upon the inferred workflow process-level metadata asmapped to the respective containers or business objects. The presentsubject matter improves document processing within the context ofworkflow processes by providing for workflow process-level metadatainference and mapping from image document annotations, as describedabove and in more detail below. As such, improved business-levelprocessing may be obtained through use of the present technology.

The process-level metadata inference and mapping from documentannotations described herein may be performed in real time to allowprompt inference and mapping of metadata, and workflow processinvocation, from annotations entered in association with documents. Forpurposes of the present description, real time shall include any timeframe of sufficiently short duration as to provide reasonable responsetime for information processing acceptable to a user of the subjectmatter described. Additionally, the term “real time” shall include whatis commonly termed “near real time”—generally meaning any time frame ofsufficiently short duration as to provide reasonable response time foron-demand information processing acceptable to a user of the subjectmatter described (e.g., within a portion of a second or within a fewseconds). These terms, while difficult to precisely define are wellunderstood by those skilled in the art.

FIG. 1 is a block diagram of an example of an implementation of a system100 for process-level metadata inference and mapping from documentannotations. A computing device_(—)1 102 through a computing device_N104 communicate via a network 106 with several other devices. The otherdevices include a workflow process server_(—)1 108 through a workflowprocess server_M 110. A metadata repository 112 stores metadata forworkflow processes performed by the workflow process server_(—)1 108through the workflow process server_M 110. A content repository 114stores documents.

For purposes of the present description, a process-level structure orcase may be established within the metadata repository 112. Theprocess-level structure or case includes process-related metadata(alternatively “case-related metadata”), such as a process/case name, aprocess/case folder, identification of documents within the contentrepository 114 that are associated with the process/case, and otherprocess/case related metadata. Similarly, the documents may include anyform of business content, including text-based documents, imagedocuments, and other forms of content that may be associated with aprocess/case.

As will be described in more detail below in association with FIG. 2through FIG. 4B, the computing device_(—)1 102 through the computingdevice_N 104 and the workflow process server_(—)1 108 through theworkflow process server_M 110 may each provide automated process-levelmetadata inference and mapping from document annotations. As such, thepresent technology may be implemented at a user computing device orserver device level. A variety of possibilities exist for implementationof the present subject matter, and all such possibilities are consideredwithin the scope of the present subject matter.

The computing device_(—)1 102 through the computing device_N 104 may beused to view and annotate documents stored within the content repository114 that are associated with a case established within the metadatarepository 112. The process-level metadata inference and mapping fromdocument annotations described herein operates to evaluate the documentannotations and to infer metadata for the case with which the respectivedocuments are associated. The computing device_(—)1 102 through thecomputing device_N 104 or the workflow process server_(—)1 108 throughthe workflow process server_M 110 may perform the inference of theworkflow process metadata from the document annotations. The workflowprocess server_(—)1 108 through the workflow process server_M 110 mayfurther operate upon or in response to the inferred metadata to performprocess-level operations. As such, the inference of process-levelmetadata from lower-level document annotations operates to invoke andautomate higher-level workflow processing tasks.

It should be noted that any of the respective computing devicesdescribed in association with FIG. 1 may be portable computing devices,either by a user's ability to move the respective computing devices todifferent locations, or by the respective computing device's associationwith a portable platform, such as a plane, train, automobile, or othermoving vehicle. It should also be noted that the respective computingdevices may be any computing devices capable of processing informationas described above and in more detail below. For example, the respectivecomputing devices may include devices such as a personal computer (e.g.,desktop, laptop, etc.) or a handheld device (e.g., cellular telephone,personal digital assistant (PDA), email device, tablet computing device,e-book reading device, etc.), a web server, an application server, orother data server device, or any other device capable of processinginformation as described above and in more detail below.

The network 106 may include any form of interconnection suitable for theintended purpose, including a private or public network such as anintranet or the Internet, respectively, direct inter-moduleinterconnection, dial-up, wireless, or any other interconnectionmechanism capable of interconnecting the respective devices.

The metadata repository 112 and the content repository 114 may includerelational databases, object databases, or any other storage type ofdevice. As such, the metadata repository 112 and the content repository114 may be implemented as appropriate for a given implementation.

FIG. 2 is a block diagram of an example of an implementation of a coreprocessing module 200 capable of performing process-level metadatainference and mapping from document annotations. The core processingmodule 200 may be associated with either the computing device_(—)1 102through the computing device_N 104 or with the server_(—)1 108 throughthe server_M 110, as appropriate for a given implementation. As such,the core processing module 200 is described generally herein, though itis understood that many variations on implementation of the componentswithin the core processing module 200 are possible and all suchvariations are within the scope of the present subject matter.

Further, the core processing module 200 may provide different andcomplementary processing of annotations and inferred/mapped metadata inassociation with each implementation. As such, for any of the examplesbelow, it is understood that any aspect of functionality described withrespect to any one device that is described in conjunction with anotherdevice (e.g., sends/sending, etc.) is to be understood to concurrentlydescribe the functionality of the other respective device (e.g.,receives/receiving, etc.).

A central processing unit (CPU) 202 (“processor”) provides hardware thatperforms computer instruction execution, computation, and othercapabilities within the core processing module 200. A display 204provides visual information to a user of the core processing module 200and an input device 206 provides input capabilities for the user.

The display 204 may include any display device, such as a cathode raytube (CRT), liquid crystal display (LCD), light emitting diode (LED),electronic ink displays, projection, touchscreen, or other displayelement or panel. The input device 206 may include a computer keyboard,a keypad, a mouse, a pen, a joystick, touchscreen, voice commandprocessing unit, or any other type of input device by which the user mayinteract with and respond to information on the display 204.

It should be noted that the display 204 and the input device 206 may beoptional components for the core processing module 200 for certainimplementations/devices, or may be located remotely from the respectivedevices and hosted by another computing device that is in communicationwith the respective devices. Accordingly, the core processing module 200may operate as a completely automated embedded device without directuser configurability or feedback. However, the core processing module200 may also provide user feedback and configurability via the display204 and the input device 206, respectively, as appropriate for a givenimplementation.

A communication module 208 provides hardware, protocol stack processing,and interconnection capabilities that allow the core processing module200 to communicate with other modules within the system 100. Thecommunication module 208 may include any electrical, protocol, andprotocol conversion capabilities useable to provide interconnectioncapabilities, as appropriate for a given implementation.

A memory 210 includes a document/annotation storage area 212 thatprovides storage for documents accessed by users and provides storagefor document annotations entered by users in association with documentsaccessed by users in association with the core processing module 200. Aninferred process-level metadata storage area 214 provides processingspace to infer case-level metadata from document annotations andprovides storage for process-level metadata (e.g., case related orworkflow related metadata) inferred from document annotations inassociation with the core processing module 200.

It should be understood that for a server-based implementation of thecore processing module 200, the documents and annotations within thedocument/annotation storage area 212 may be imported either from acomputing device or from the content repository 114 after theannotations are added by a user of a computer device. Alternatively, fora client-computing device-based implementation, the documents andannotations may be stored locally prior to being migrated to the contentrepository 114 or to one of the workflow process server_(—)1 108 throughthe workflow process server_M 110. Additionally, as described above, anyof the workflow process server_(—)1 108 through the workflow processserver_M 110 and the computing device_(—)1 102 through the computingdevice_N 104 may perform the inference of process-level metadata fromthe document annotations.

It is understood that the memory 210 may include any combination ofvolatile and non-volatile memory suitable for the intended purpose,distributed or localized as appropriate, and may include other memorysegments not illustrated within the present example for ease ofillustration purposes. For example, the memory 210 may include a codestorage area, an operating system storage area, a code execution area,and a data area without departure from the scope of the present subjectmatter.

A process-level metadata inference module 216 is also illustrated. Theprocess-level metadata inference module 216 provides document annotationanalysis and process-level inference of metadata from analyzedannotations for the core processing module 200, as described above andin more detail below. The process-level metadata inference module 216implements the automated process-level metadata inference and mappingfrom document annotations of the core processing module 200.

It should also be noted that the process-level metadata inference module216 may form a portion of other circuitry described without departurefrom the scope of the present subject matter. Further, the process-levelmetadata inference module 216 may alternatively be implemented as anapplication stored within the memory 210. In such an implementation, theprocess-level metadata inference module 216 may include instructionsexecuted by the CPU 202 for performing the functionality describedherein. The CPU 202 may execute these instructions to provide theprocessing capabilities described above and in more detail below for thecore processing module 200. The process-level metadata inference module216 may form a portion of an interrupt service routine (ISR), a portionof an operating system, a portion of a browser application, or a portionof a separate application without departure from the scope of thepresent subject matter.

The metadata repository 112 and the content repository 114 are againshown within FIG. 2 associated with the core processing module 200. Assuch, the metadata repository 112 and the content repository 114 may beoperatively coupled to the core processing module 200 without use ofnetwork connectivity, as appropriate for a given implementation.

The CPU 202, the display 204, the input device 206, the communicationmodule 208, the memory 210, the process-level metadata inference module216, the metadata repository 112, and the content repository 114 areinterconnected via an interconnection 218. The interconnection 218 mayinclude a system bus, a network, or any other interconnection capable ofproviding the respective components with suitable interconnection forthe respective purpose.

Though the different modules illustrated within FIG. 2 are illustratedas component-level modules for ease of illustration and descriptionpurposes, it should be noted that these modules may include anyhardware, programmed processor(s), and memory used to carry out thefunctions of the respective modules as described above and in moredetail below. For example, the modules may include additional controllercircuitry in the form of application specific integrated circuits(ASICs), processors, antennas, and/or discrete integrated circuits andcomponents for performing communication and electrical controlactivities associated with the respective modules. Additionally, themodules may include interrupt-level, stack-level, and application-levelmodules as appropriate. Furthermore, the modules may include any memorycomponents used for storage, execution, and data processing forperforming processing activities associated with the respective modules.The modules may also form a portion of other circuitry described or maybe combined without departure from the scope of the present subjectmatter.

Additionally, while the core processing module 200 is illustrated withand has certain components described, other modules and components maybe associated with the core processing module 200 without departure fromthe scope of the present subject matter. Additionally, it should benoted that, while the core processing module 200 is described as asingle device for ease of illustration purposes, the components withinthe core processing module 200 may be co-located or distributed andinterconnected via a network without departure from the scope of thepresent subject matter. For a distributed arrangement, the display 204and the input device 206 may be located at a point of sale device,kiosk, or other location, while the CPU 202 and memory 210 may belocated at a local or remote server. Many other possible arrangementsfor components of the core processing module 200 are possible and allare considered within the scope of the present subject matter. It shouldalso be understood that, though the metadata repository 112 and thecontent repository 114 are illustrated as separate components forpurposes of example, the information stored within the metadatarepository 112 and the content repository 114 may also/alternatively bestored within the memory 210 without departure from the scope of thepresent subject matter. Accordingly, the core processing module 200 maytake many forms and may be associated with many platforms.

FIG. 3 through FIG. 4B described below represent example processes thatmay be executed by devices, such as the core processing module 200, toperform the automated process-level metadata inference and mapping fromdocument annotations associated with the present subject matter. Manyother variations on the example processes are possible and all areconsidered within the scope of the present subject matter. The exampleprocesses may be performed by modules, such as the process-levelmetadata inference module 216 and/or executed by the CPU 202, associatedwith such devices. It should be noted that time out procedures and othererror control procedures are not illustrated within the exampleprocesses described below for ease of illustration purposes. However, itis understood that all such procedures are considered to be within thescope of the present subject matter. Further, the described processesmay be combined, sequences of the processing described may be changed,and additional processing may be added or removed without departure fromthe scope of the present subject matter.

FIG. 3 is a flow chart of an example of an implementation of a process300 for process-level metadata inference and mapping from documentannotations. At block 302, the process 300 detects, by a processor, auser annotation entered in association with a content document of aworkflow process executed in association with a metadata context-drivenprocessing system. At block 304, the process 300 analyzes the userannotation entered in association with the content document according toa process-level context associated with the content document within theworkflow process. At block 306, the process 300 infers process-levelmetadata of the workflow process based upon the analysis of the userannotation according to the process-level context. At block 308, theprocess 300 stores the inferred process-level metadata as part of theprocess-level context of the workflow process.

FIGS. 4A-4B are flow charts of an example of an implementation of aprocess 400 for process-level metadata inference and mapping fromdocument annotations by correlation of categorized annotation contentand available process-level metadata values of related process-levelmetadata types, and mapping from inferred process-level metadata tocontent-level metadata of other content items. FIG. 4A illustratesinitial processing within the process 400. At decision point 402, theprocess 400 makes a determination as to whether a content annotation hasbeen detected in association with a content item of a workflow process.As described above, content items associated with a workflow process mayinclude documents, and annotations may include hand-written orprogrammatically entered notations of a user's analysis of the document.

In response to determining at decision point 402 that a contentannotation has been detected, the process 400 captures content of theannotation and analyzes the annotation content at block 404. Capture andanalysis of the annotation content may include, for example, opticalcharacter recognition (OCR), handwriting analysis, or other form captureand analysis of the annotation content as appropriate for the givenimplementation.

At block 406, the process 400 categorizes the annotation based uponavailable annotation types. For example, annotation types may includegraphical elements such as arrows, text-based annotations, or otherforms of annotations as appropriate for a given implementation.

At block 408, the process 400 identifies the relationship of/between theannotated content to a process-level container that contains the contentitem with which the annotation was detected. For example, therelationship between annotated content and a process-level container mayinclude identification of a type of container object with which thecontent item is associated.

At block 410, the process 400 obtains a list of process-level metadatatypes for the identified process-level container. Example metadata typesmay include process-level user decision fields (e.g., a radiologist'sdecision regarding further treatment of a patient, a loan officer'sdecision regarding a loan application, etc.) and other forms of metadataas appropriate for a given implementation.

At block 412, the process 400 identifies a relationship between thecategorized annotation type of the annotation and the process-levelmetadata types. It should be understood that there may be multipleprocess-level metadata types that result in relationships with thecategorized annotation type of the detected annotation. For example, thetext-based annotation entered by a user may be determined to be relatedto a process-level user decision field, such as where a radiologist hasentered a text notation that a patient needs to have a cast applied to abone fracture.

At block 414, the process 400 determines available process-levelmetadata values for the related process-level metadata types. Continuingwith the present example, an available process-level metadata value mayinclude a process-level field that identifies a next location within ahospital to which a patient should be moved after the radiologistreviews an x-ray.

At block 416, the process 400 correlates the annotation content withavailable process-level metadata values of the related process-levelmetadata types. Again, continuing with the present example, the process400 may correlate the radiologist's decision that the patient needs acast with a triage room location identifier within a hospital where acast may be applied to the bone fracture.

It should be understood, that for any given implementation, there may bemultiple potential correlations between annotation content and availableprocess-level metadata values. As such, at block 418, the process 400identifies a highest-correlation between annotation content andavailable process-level metadata values for the related process-levelmetadata types.

At block 420, the process 400 selects the process-level metadata valuefrom the available process-level values for the process-level metadatawith the highest correlation to the detected annotation content. Atblock 422, the process 400 assigns the selected process-level metadatavalue as a new process-level metadata value for the container objectwith which the content item/document is associated.

At decision point 424, the process 400 makes a determination as towhether to update content-level metadata of other content within theprocess-level container based upon the inferred process-level metadata.In response to determining not to update content-level metadata of othercontent within the process-level container based upon the inferredprocess-level metadata, the process 400 returns to decision point 402and iterates as described above. In response to determining at decisionpoint 424 to update content-level metadata of other content within theprocess-level container based upon the inferred process-level metadata,the process 400 transitions to the processing shown and described inassociation with FIG. 4B.

FIG. 4B illustrates additional processing associated with the process400 for process-level metadata inference and mapping from documentannotations by correlation of categorized annotation content andavailable process-level metadata values of related process-levelmetadata types, and mapping from inferred process-level metadata tocontent-level metadata of other content items. At block 426, the process400 identifies the relationship of/between the inferred-process-levelmetadata and content-level metadata of other content item(s) in theprocess-level container for which the process-level metadata wasinferred. For example, the relationship between inferred process-levelmetadata and content-level metadata may include identification of a typeof content item with which the process-level metadata is associated. Itis understood that multiple content items may be determined to berelated to the inferred and updated process-level metadata. As such, theprocessing described below applies to each identified related contentitem.

At decision point 428, the process 400 makes a determination as towhether any content-level metadata has a relationship to the inferredand updated process-level metadata. In response to determining thatthere is content-level metadata with a relationship to the inferred andupdated process-level metadata, the process 400 obtains a list ofcontent-level metadata types for the identified content-level item(s)with the determined relationship to the inferred process-level metadataat block 430. Example metadata types may include content-level userdecision fields (e.g., an invoice document that is to be updated todocument an x-ray, where the invoice document metadata is to be updatedto indicate that the invoice is to be reviewed and signed off on by aradiology department, updating a property inspection request document inresponse to a loan officer's decision to approve a loan application,etc.) and other forms of metadata as appropriate for a givenimplementation.

At block 432, the process 400 identifies a relationship between theinferred process-level metadata and related content-level metadatatypes. It should be understood that there may be multiple content-levelmetadata types that result in relationships with the inferredprocess-level metadata. For example, the inferred process-level metadatamay be determined to be related to a content-level user decision fieldin another document, such as where emergency room personnel that are onduty are to be added to a document that tracks persons available toattend to a patient.

At block 434, the process 400 determines available content-levelmetadata values for the related content-level metadata types. Continuingwith the present example, an available content-level metadata value mayinclude a content-level field of another related document thatidentifies an attending physician that applies a cast to a patient'sbone fracture.

At block 436, the process 400 selects the content-level metadata valuefrom the available content-level metadata values for the content-levelmetadata. At block 438, the process 400 assigns the selectedcontent-level metadata value(s) as new content-level metadata value(s)for the related content object(s) with which the inferred and updatedprocess-level metadata is associated.

In response to assigning the selected content-level metadata value(s) asnew content-level metadata value(s) for the related content object(s)with which the inferred and updated process-level metadata is associatedat block 438, or in response to determining at decision point 428 thatthere are no content-level metadata items that have a relationship tothe inferred and updated process-level metadata, the process 400 returnsto FIG. 4A at decision point 402 and iterates as described above.

It should be noted that further processing may be associated with theprocess 400, such as invoking process-level actions responsive tochanges in individual items of process-level metadata values. Forexample, the process 400 may generate a notification to a nursingstation to alert a nurse that the patient needs to be moved to thetriage location of the hospital. This additional processing is notillustrated, but is considered to form a part of the processingassociated with the process 400.

As such, the process 400 detects annotations to documents, and analyzesand categorizes the detected annotations. The process 400 identifiesrelationships between the annotation content and process-level containermetadata types and values. The process 400 further correlates theannotation content with available process-level metadata values andselects a highest-correlated process-level metadata value to update. Theprocess 400 assigns the selected process-level metadata value with a newprocess-level metadata value based upon the analysis and correlation ofthe annotation content with the respective container object. As such,the process 400 updates a process-level metadata value for a containerobject (e.g., a case or case folder) with a new process-level metadatavalue derived from content of the annotation. The process 400 furtherupdates other related content items/documents within the process-levelcontext of a workflow process that have relationships with the inferredand updated process-level metadata values. The process 400 may furtherinvoke workflow processing based upon the assigned process-levelmetadata value.

As described above in association with FIG. 1 through FIG. 4B, theexample systems and processes provide process-level metadata inferenceand mapping from document annotations. Many other variations andadditional activities associated with process-level metadata inferenceand mapping from document annotations are possible and all areconsidered within the scope of the present subject matter.

Those skilled in the art will recognize, upon consideration of the aboveteachings, that certain of the above examples are based upon use of aprogrammed processor, such as the CPU 202. However, the invention is notlimited to such example embodiments, since other embodiments could beimplemented using hardware component equivalents such as special purposehardware and/or dedicated processors. Similarly, general purposecomputers, microprocessor based computers, micro-controllers, opticalcomputers, analog computers, dedicated processors, application specificcircuits and/or dedicated hard wired logic may be used to constructalternative equivalent embodiments.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art basedupon the teachings herein without departing from the scope and spirit ofthe invention. The subject matter was described to explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1.-7. (canceled)
 8. A system, comprising: a memory; and a processorprogrammed to: detect a user annotation entered in association with acontent document of a workflow process executed in association with ametadata context-driven processing system; analyze the user annotationentered in association with the content document according to aprocess-level context associated with the content document within theworkflow process; infer process-level metadata of the workflow processbased upon the analysis of the user annotation according to theprocess-level context; and store the inferred process-level metadatawithin the memory as part of the process-level context of the workflowprocess.
 9. The system of claim 8, where, in being programmed to analyzethe user annotation entered in association with the content documentaccording to the process-level context associated with the contentdocument within the workflow process, the processor is programmed to:categorize the user annotation based upon available annotation types;and identify a relationship between content of the user annotation and aprocess-level container that contains the content document within theworkflow process.
 10. The system of claim 8, where, in being programmedto infer the process-level metadata of the workflow process based uponthe analysis of the user annotation according to the process-levelcontext, the processor is programmed to: identify a relationship betweena categorized annotation type of the user annotation and process-levelmetadata types within a list of process-level metadata types; determineavailable process-level metadata values of the related process-levelmetadata types; correlate content of the user annotation with theavailable process-level metadata values of the related process-levelmetadata types; and assign a new process-level metadata value based uponthe content of the user annotation to a highest-correlated availableprocess-level metadata value.
 11. The system of claim 8, where, in beingprogrammed to infer the process-level metadata of the workflow processbased upon the analysis of the user annotation according to theprocess-level context, the processor is programmed to: identify theprocess-level context as a case associated with a customer entity;determine process-level metadata types associated with the case; andupdate a process-level metadata value of the case with a newprocess-level metadata value derived from content of the userannotation.
 12. The system of claim 8, where the content documentcomprises a content entity selected from a group consisting of a form,an image, a user request, an application, a portable document format(PDF) document, and a text document.
 13. The system of claim 8, wherethe processor is further programmed to: determine that the inferredprocess-level metadata is related to content-level metadata of at leastone other content document within the process-level context of theworkflow process; and update the related content-level metadata of theat least one other content document within the process-level context ofthe workflow process based upon the inferred process-level metadata. 14.A computer program product, comprising: a computer readable storagemedium having computer readable program code embodied therewith, wherethe computer readable program code when executed on a computer causesthe computer to: detect a user annotation entered in association with acontent document of a workflow process executed in association with ametadata context-driven processing system; analyze the user annotationentered in association with the content document according to aprocess-level context associated with the content document within theworkflow process; infer process-level metadata of the workflow processbased upon the analysis of the user annotation according to theprocess-level context; and store the inferred process-level metadata aspart of the process-level context of the workflow process.
 15. Thecomputer program product of claim 14, where, in causing the computer toanalyze the user annotation entered in association with the contentdocument according to the process-level context associated with thecontent document within the workflow process, the computer readableprogram code when executed on the computer causes the computer to:categorize the user annotation based upon available annotation types;and identify a relationship between content of the user annotation and aprocess-level container that contains the content document within theworkflow process.
 16. The computer program product of claim 14, where,in causing the computer to infer the process-level metadata of theworkflow process based upon the analysis of the user annotationaccording to the process-level context, the computer readable programcode when executed on the computer causes the computer to: identify arelationship between a categorized annotation type of the userannotation and process-level metadata types within a list ofprocess-level metadata types; determine available process-level metadatavalues of the related process-level metadata types; correlate content ofthe user annotation with the available process-level metadata values ofthe related process-level metadata types; and assign a new process-levelmetadata value based upon the content of the user annotation to ahighest-correlated available process-level metadata value.
 17. Thecomputer program product of claim 14, where, in causing the computer toinfer the process-level metadata of the workflow process based upon theanalysis of the user annotation according to the process-level context,the computer readable program code when executed on the computer causesthe computer to: identify the process-level context as a case associatedwith a customer entity; determine process-level metadata typesassociated with the case; and update a process-level metadata value ofthe case with a new process-level metadata value derived from content ofthe user annotation.
 18. The computer program product of claim 14, wherethe content document comprises a content entity selected from a groupconsisting of a form, an image, a user request, an application, aportable document format (PDF) document, and a text document.
 19. Thecomputer program product of claim 14, where the computer readableprogram code when executed on the computer further causes the computerto: determine that the inferred process-level metadata is related tocontent-level metadata of at least one other content document within theprocess-level context of the workflow process; and update the relatedcontent-level metadata of the at least one other content document withinthe process-level context of the workflow process based upon theinferred process-level metadata.
 20. The computer program product ofclaim 14, where the process-level context comprises a workflowrelationship object selected from a group consisting of a container, afolder, a case, and a request.